Stop calling the upstack push a force-push in the README#41
Merged
Conversation
The action only fast-forwards updated branches; the synthetic merge commit is built as a descendant of the old head precisely so the push is not a force-push. The README claimed otherwise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "How it works" list described step 5 as force-pushing updated branches. There is no force push in the action: the synthetic merge commit is built as a descendant of the child's old head precisely so the push is a fast-forward (which keeps the PR mergeable and the
synchronizeresume firing). Dropped the word "force".Generated by Claude Code